Thanks a lot!

We can merge this, but I was thinking, maybe we should automate this, otherwise it will inevitably fall out of date every time

Here’s what I had in mind:

• Run a GitHub Actions cron job every day at 00:00 inside v6-docs
• This job executes a small JS script using Octokit, which fetches releases across our repos and checks for new one
• The script updates our releases.json, making sure to dedupe entries that are already documented. Then it commits the updated file back to the repo.
• Sometimes we probably don’t want to include certain releases (eg. "update dependencies" releases). For that, we could introduce a simple opt-in flag in the release notes itself. For example, appending [inside_v6_docs] ( we can find better naming/flag) at the end of a release description. Our script would only include releases that contain this flag when updating the docs page

Yes, I am fully aware of that. I made this change in order to provide a fresher page following my proposal to add AdonisJS to Endoflife.date.
I was also considering exploring the possibility of suggesting an automation solution afterwards.